Configuring synchronization signal blocks having different power levels

ABSTRACT

Apparatuses, methods, and systems are disclosed for synchronization signal block reception and synchronization signal block transmission. One apparatus for synchronization signal block reception includes a receiver that receives multiple synchronization signal blocks. The multiple synchronization signal blocks have different power levels corresponding to at least two synchronization signal blocks of the multiple synchronization signal blocks.

CROSS REFERENCE TO RELATED APPLICATIONS

This application is a continuation of application Ser. No. 16/623,119filed on Dec. 16, 2019, which is hereby incorporated by reference in itsentirety.

FIELD

The subject matter disclosed herein relates generally to wirelesscommunications and more particularly relates to synchronization signalblock transmission.

BACKGROUND

The following abbreviations are herewith defined, at least some of whichare referred to within the following description: Third GenerationPartnership Project (“3GPP”), Positive-Acknowledgment (“ACK”), BinaryPhase Shift Keying (“BPSK”), Clear Channel Assessment (“CCA”), CyclicPrefix (“CP”), Cyclical Redundancy Check (“CRC”), Channel StateInformation (“CSI”), Common Search Space (“CSS”), Discrete FourierTransform Spread (“DFTS”), Downlink Control Information (“DCI”),Downlink (“DL”), Downlink Pilot Time Slot (“DwPTS”), Enhanced ClearChannel Assessment (“eCCA”), Enhanced Mobile Broadband (“eMBB”), EvolvedNode B (“eNB”), European Telecommunications Standards Institute(“ETSI”), Frame Based Equipment (“FBE”), Frequency Division Duplex(“FDD”), Frequency Division Multiple Access (“FDMA”), Guard Period(“GP”), Hybrid Automatic Repeat Request (“HARQ”), Internet-of-Things(“IoT”), Licensed Assisted Access (“LAA”), Load Based Equipment (“LBE”),Listen-Before-Talk (“LBT”), Long Term Evolution (“LTE”), Multiple Access(“MA”), Modulation Coding Scheme (“MCS”), Machine Type Communication(“MTC”), Multiple Input Multiple Output (“MIMO”), Multi User SharedAccess (“MUSA”), Narrowband (“NB”), Negative-Acknowledgment (“NACK”) or(“NAK”), Next Generation Node B (“gNB”), Non-Orthogonal Multiple Access(“NOMA”), Orthogonal Frequency Division Multiplexing (“OFDM”), PrimaryCell (“PCell”), Physical Broadcast Channel (“PBCH”), Physical DownlinkControl Channel (“PDCCH”), Physical Downlink Shared Channel (“PDSCH”),Pattern Division Multiple Access (“PDMA”), Physical Hybrid ARQ IndicatorChannel (“PHICH”), Physical Random Access Channel (“PRACH”), PhysicalResource Block (“PRB”), Physical Uplink Control Channel (“PUCCH”),Physical Uplink Shared Channel (“PUSCH”), Quality of Service (“QoS”),Quadrature Phase Shift Keying (“QPSK”), Radio Resource Control (“RRC”),Random Access Procedure (“RACH”), Random Access Response (“RAR”), RadioNetwork Temporary Identifier (“RNTI”), Reference Signal (“RS”), ResourceSpread Multiple Access (“RSMA”), Round Trip Time (“RTT”), Receive(“RX”), Sparse Code Multiple Access (“SCMA”), Scheduling Request (“SR”),Single Carrier Frequency Division Multiple Access (“SC-FDMA”), SecondaryCell (“SCell”), Shared Channel (“SCH”),Signal-to-Interference-Plus-Noise Ratio (“SINR”), System InformationBlock (“SIB”), Transport Block (“TB”), Transport Block Size (“TBS”),Time-Division Duplex (“TDD”), Time Division Multiplex (“TDM”),Transmission Time Interval (“TTI”), Transmit (“TX”), Uplink ControlInformation (“UCI”), User Entity/Equipment (Mobile Terminal) (“UE”),Uplink (“UL”), Universal Mobile Telecommunications System (“UMTS”),Uplink Pilot Time Slot (“UpPTS”), Ultra-reliability and Low-latencyCommunications (“URLLC”), and Worldwide Interoperability for MicrowaveAccess (“WiMAX”). As used herein, “HARQ-ACK” may represent collectivelythe Positive Acknowledge (“ACK”) and the Negative Acknowledge (“NACK”).ACK means that a TB is correctly received while NACK (or NAK) means a TBis erroneously received.

In certain wireless communications networks, multiple transmission beamsmay be used. In such configurations, coverage of the multipletransmission beams from different cells may overlap.

BRIEF SUMMARY

Apparatuses for synchronization signal block reception are disclosed.Methods and systems also perform the functions of the apparatus. In oneembodiment, the apparatus includes a receiver that receives multiplesynchronization signal blocks having different power levels.

In one embodiment, the receiver receives power information correspondingto the power levels of the multiple synchronization signal blocks inradio resource control signaling. In a further embodiment, the apparatusincludes a processor that determines a normalized reference signalreceived power corresponding to each synchronization signal block of themultiple synchronization signal blocks using the power information. Incertain embodiments, the processor compares the normalized referencesignal received power corresponding to each synchronization signal blockof the multiple synchronization signal blocks. In various embodiments,the apparatus includes a transmitter that transmits feedbackcorresponding to the comparison of the normalized reference signalreceived power corresponding to each synchronization signal block of themultiple synchronization signal blocks. In some embodiments, thereceiver receives nominal power information corresponding to the powerlevels of the multiple synchronization signal blocks in systeminformation blocks.

In certain embodiments, the receiver receives power offset informationcorresponding to the power levels of the multiple synchronization signalblocks in system information blocks, radio resource control signaling,or some combination thereof. In some embodiments, the receiver receivespower information corresponding to channel state information referencesignals in radio resource control signaling. In various embodiments, thepower information includes nominal power information, power offsetinformation, or some combination thereof.

In one embodiment, the apparatus includes a processor that determines anormalized reference signal received power corresponding to channelstate information reference signals using the power information. Incertain embodiments, the receiver receives channel state informationreference signal ports within a channel state information referencesignal resource at a same transmission power level. In some embodiments,the receiver receives different channel state information referencesignal resources at different transmission power levels. In variousembodiments, the receiver receives power information corresponding tochannel state information reference signal resources in radio resourcecontrol signaling. In one embodiment, the power information includesnominal power information, power offset information, or some combinationthereof.

A method for synchronization signal block reception, in one embodiment,includes receiving multiple synchronization signal blocks havingdifferent power levels.

In one embodiment, an apparatus for synchronization signal blocktransmission includes a processor that determines power levelscorresponding to each synchronization signal block of multiplesynchronization signal blocks transmitted using multiple transmit beams.In some embodiments, the apparatus includes a transmitter that transmitsthe multiple synchronization signal blocks based on the power levelsusing the multiple transmit beams.

In certain embodiments, the transmitter transmits power informationcorresponding to the power levels of the multiple synchronization signalblocks in radio resource control signaling. In various embodiments, thetransmitter transmits nominal power information corresponding to thepower levels of the multiple synchronization signal blocks in systeminformation blocks. In some embodiments, the transmitter transmits poweroffset information corresponding to the power levels of the multiplesynchronization signal blocks in system information blocks, radioresource control signaling, or some combination thereof.

In certain embodiments, the transmitter transmits power informationcorresponding to channel state information reference signals in radioresource control signaling. In some embodiments, the power informationincludes nominal power information, power offset information, or somecombination thereof. In various embodiments, the transmitter transmitschannel state information reference signal ports within a channel stateinformation reference signal resource at a same transmission powerlevel. In one embodiment, the transmitter transmits different channelstate information reference signal resources at different transmissionpower levels. In certain embodiments, the transmitter transmits powerinformation corresponding to channel state information reference signalresources in radio resource control signaling. In various embodiments,the power information includes nominal power information, power offsetinformation, or some combination thereof.

A method for synchronization signal block transmission, in oneembodiment, includes determining power levels corresponding to eachsynchronization signal block of multiple synchronization signal blockstransmitted using multiple transmit beams. In some embodiments, themethod includes transmitting the multiple synchronization signal blocksbased on the power levels using the multiple transmit beams.

BRIEF DESCRIPTION OF THE DRAWINGS

A more particular description of the embodiments briefly described abovewill be rendered by reference to specific embodiments that areillustrated in the appended drawings. Understanding that these drawingsdepict only some embodiments and are not therefore to be considered tobe limiting of scope, the embodiments will be described and explainedwith additional specificity and detail through the use of theaccompanying drawings, in which:

FIG. 1 is a schematic block diagram illustrating one embodiment of awireless communication system for synchronization signal blocktransmission and/or reception;

FIG. 2 is a schematic block diagram illustrating one embodiment of anapparatus that may be used for synchronization signal block reception;

FIG. 3 is a schematic block diagram illustrating one embodiment of anapparatus that may be used for synchronization signal blocktransmission;

FIG. 4 is a schematic flow chart diagram illustrating one embodiment ofa method for synchronization signal block reception; and

FIG. 5 is a schematic flow chart diagram illustrating one embodiment ofa method for synchronization signal block transmission.

DETAILED DESCRIPTION

As will be appreciated by one skilled in the art, aspects of theembodiments may be embodied as a system, apparatus, method, or programproduct. Accordingly, embodiments may take the form of an entirelyhardware embodiment, an entirely software embodiment (includingfirmware, resident software, micro-code, etc.) or an embodimentcombining software and hardware aspects that may all generally bereferred to herein as a “circuit,” “module” or “system.” Furthermore,embodiments may take the form of a program product embodied in one ormore computer readable storage devices storing machine readable code,computer readable code, and/or program code, referred hereafter as code.The storage devices may be tangible, non-transitory, and/ornon-transmission. The storage devices may not embody signals. In acertain embodiment, the storage devices only employ signals foraccessing code.

Certain of the functional units described in this specification may belabeled as modules, in order to more particularly emphasize theirimplementation independence. For example, a module may be implemented asa hardware circuit comprising custom very-large-scale integration(“VLSI”) circuits or gate arrays, off-the-shelf semiconductors such aslogic chips, transistors, or other discrete components. A module mayalso be implemented in programmable hardware devices such as fieldprogrammable gate arrays, programmable array logic, programmable logicdevices or the like.

Modules may also be implemented in code and/or software for execution byvarious types of processors. An identified module of code may, forinstance, include one or more physical or logical blocks of executablecode which may, for instance, be organized as an object, procedure, orfunction. Nevertheless, the executables of an identified module need notbe physically located together, but may include disparate instructionsstored in different locations which, when joined logically together,include the module and achieve the stated purpose for the module.

Indeed, a module of code may be a single instruction, or manyinstructions, and may even be distributed over several different codesegments, among different programs, and across several memory devices.Similarly, operational data may be identified and illustrated hereinwithin modules, and may be embodied in any suitable form and organizedwithin any suitable type of data structure. The operational data may becollected as a single data set, or may be distributed over differentlocations including over different computer readable storage devices.Where a module or portions of a module are implemented in software, thesoftware portions are stored on one or more computer readable storagedevices.

Any combination of one or more computer readable medium may be utilized.The computer readable medium may be a computer readable storage medium.The computer readable storage medium may be a storage device storing thecode. The storage device may be, for example, but not limited to, anelectronic, magnetic, optical, electromagnetic, infrared, holographic,micromechanical, or semiconductor system, apparatus, or device, or anysuitable combination of the foregoing.

More specific examples (a non-exhaustive list) of the storage devicewould include the following: an electrical connection having one or morewires, a portable computer diskette, a hard disk, a random access memory(“RAM”), a read-only memory (“ROM”), an erasable programmable read-onlymemory (“EPROM” or Flash memory), a portable compact disc read-onlymemory (“CD-ROM”), an optical storage device, a magnetic storage device,or any suitable combination of the foregoing. In the context of thisdocument, a computer readable storage medium may be any tangible mediumthat can contain, or store a program for use by or in connection with aninstruction execution system, apparatus, or device.

Code for carrying out operations for embodiments may be any number oflines and may be written in any combination of one or more programminglanguages including an object oriented programming language such asPython, Ruby, Java, Smalltalk, C++, or the like, and conventionalprocedural programming languages, such as the “C” programming language,or the like, and/or machine languages such as assembly languages. Thecode may execute entirely on the user's computer, partly on the user'scomputer, as a stand-alone software package, partly on the user'scomputer and partly on a remote computer or entirely on the remotecomputer or server. In the latter scenario, the remote computer may beconnected to the user's computer through any type of network, includinga local area network (“LAN”) or a wide area network (“WAN”), or theconnection may be made to an external computer (for example, through theInternet using an Internet Service Provider).

Reference throughout this specification to “one embodiment,” “anembodiment,” or similar language means that a particular feature,structure, or characteristic described in connection with the embodimentis included in at least one embodiment. Thus, appearances of the phrases“in one embodiment,” “in an embodiment,” and similar language throughoutthis specification may, but do not necessarily, all refer to the sameembodiment, but mean “one or more but not all embodiments” unlessexpressly specified otherwise. The terms “including,” “comprising,”“having,” and variations thereof mean “including but not limited to,”unless expressly specified otherwise. An enumerated listing of itemsdoes not imply that any or all of the items are mutually exclusive,unless expressly specified otherwise. The terms “a,” “an,” and “the”also refer to “one or more” unless expressly specified otherwise.

Furthermore, the described features, structures, or characteristics ofthe embodiments may be combined in any suitable manner. In the followingdescription, numerous specific details are provided, such as examples ofprogramming, software modules, user selections, network transactions,database queries, database structures, hardware modules, hardwarecircuits, hardware chips, etc., to provide a thorough understanding ofembodiments. One skilled in the relevant art will recognize, however,that embodiments may be practiced without one or more of the specificdetails, or with other methods, components, materials, and so forth. Inother instances, well-known structures, materials, or operations are notshown or described in detail to avoid obscuring aspects of anembodiment.

Aspects of the embodiments are described below with reference toschematic flowchart diagrams and/or schematic block diagrams of methods,apparatuses, systems, and program products according to embodiments. Itwill be understood that each block of the schematic flowchart diagramsand/or schematic block diagrams, and combinations of blocks in theschematic flowchart diagrams and/or schematic block diagrams, can beimplemented by code. The code may be provided to a processor of ageneral purpose computer, special purpose computer, or otherprogrammable data processing apparatus to produce a machine, such thatthe instructions, which execute via the processor of the computer orother programmable data processing apparatus, create means forimplementing the functions/acts specified in the schematic flowchartdiagrams and/or schematic block diagrams block or blocks.

The code may also be stored in a storage device that can direct acomputer, other programmable data processing apparatus, or other devicesto function in a particular manner, such that the instructions stored inthe storage device produce an article of manufacture includinginstructions which implement the function/act specified in the schematicflowchart diagrams and/or schematic block diagrams block or blocks.

The code may also be loaded onto a computer, other programmable dataprocessing apparatus, or other devices to cause a series of operationalsteps to be performed on the computer, other programmable apparatus orother devices to produce a computer implemented process such that thecode which execute on the computer or other programmable apparatusprovide processes for implementing the functions/acts specified in theflowchart and/or block diagram block or blocks.

The schematic flowchart diagrams and/or schematic block diagrams in theFigures illustrate the architecture, functionality, and operation ofpossible implementations of apparatuses, systems, methods and programproducts according to various embodiments. In this regard, each block inthe schematic flowchart diagrams and/or schematic block diagrams mayrepresent a module, segment, or portion of code, which includes one ormore executable instructions of the code for implementing the specifiedlogical function(s).

It should also be noted that, in some alternative implementations, thefunctions noted in the block may occur out of the order noted in theFigures. For example, two blocks shown in succession may, in fact, beexecuted substantially concurrently, or the blocks may sometimes beexecuted in the reverse order, depending upon the functionalityinvolved. Other steps and methods may be conceived that are equivalentin function, logic, or effect to one or more blocks, or portionsthereof, of the illustrated Figures.

Although various arrow types and line types may be employed in theflowchart and/or block diagrams, they are understood not to limit thescope of the corresponding embodiments. Indeed, some arrows or otherconnectors may be used to indicate only the logical flow of the depictedembodiment. For instance, an arrow may indicate a waiting or monitoringperiod of unspecified duration between enumerated steps of the depictedembodiment. It will also be noted that each block of the block diagramsand/or flowchart diagrams, and combinations of blocks in the blockdiagrams and/or flowchart diagrams, can be implemented by specialpurpose hardware-based systems that perform the specified functions oracts, or combinations of special purpose hardware and code.

The description of elements in each figure may refer to elements ofproceeding figures. Like numbers refer to like elements in all figures,including alternate embodiments of like elements.

FIG. 1 depicts an embodiment of a wireless communication system 100 forsynchronization signal block transmission and/or reception. In oneembodiment, the wireless communication system 100 includes remote units102 and base units 104. Even though a specific number of remote units102 and base units 104 are depicted in FIG. 1 , one of skill in the artwill recognize that any number of remote units 102 and base units 104may be included in the wireless communication system 100.

In one embodiment, the remote units 102 may include computing devices,such as desktop computers, laptop computers, personal digital assistants(“PDAs”), tablet computers, smart phones, smart televisions (e.g.,televisions connected to the Internet), set-top boxes, game consoles,security systems (including security cameras), vehicle on-boardcomputers, network devices (e.g., routers, switches, modems), or thelike. In some embodiments, the remote units 102 include wearabledevices, such as smart watches, fitness bands, optical head-mounteddisplays, or the like. Moreover, the remote units 102 may be referred toas subscriber units, mobiles, mobile stations, users, terminals, mobileterminals, fixed terminals, subscriber stations, UE, user terminals, adevice, or by other terminology used in the art. The remote units 102may communicate directly with one or more of the base units 104 via ULcommunication signals.

The base units 104 may be distributed over a geographic region. Incertain embodiments, a base unit 104 may also be referred to as anaccess point, an access terminal, a base, a base station, a Node-B, aneNB, a gNB, a Home Node-B, a relay node, a device, or by any otherterminology used in the art. The base units 104 are generally part of aradio access network that includes one or more controllers communicablycoupled to one or more corresponding base units 104. The radio accessnetwork is generally communicably coupled to one or more core networks,which may be coupled to other networks, like the Internet and publicswitched telephone networks, among other networks. These and otherelements of radio access and core networks are not illustrated but arewell known generally by those having ordinary skill in the art.

In one implementation, the wireless communication system 100 iscompliant with the 3GPP protocol, wherein the base unit 104 transmitsusing an OFDM modulation scheme on the DL and the remote units 102transmit on the UL using a SC-FDMA scheme or an OFDM scheme. Moregenerally, however, the wireless communication system 100 may implementsome other open or proprietary communication protocol, for example,WiMAX, among other protocols. The present disclosure is not intended tobe limited to the implementation of any particular wirelesscommunication system architecture or protocol.

The base units 104 may serve a number of remote units 102 within aserving area, for example, a cell or a cell sector via a wirelesscommunication link. The base units 104 transmit DL communication signalsto serve the remote units 102 in the time, frequency, and/or spatialdomain.

In one embodiment, a remote unit 102 may receive multiplesynchronization signal blocks having different power levels (e.g., atleast two synchronization signal blocks have different power levels).Accordingly, a remote unit 102 may be used for synchronization signalblock reception.

In certain embodiments, a base unit 104 may determine power levelscorresponding to each synchronization signal block of multiplesynchronization signal blocks transmitted using multiple transmit beams.In some embodiments, the base unit 104 may transmit the multiplesynchronization signal blocks based on the power levels using themultiple transmit beams. Accordingly, a base unit 104 may be used forsynchronization signal block transmission.

FIG. 2 depicts one embodiment of an apparatus 200 that may be used forsynchronization signal block reception. The apparatus 200 includes oneembodiment of the remote unit 102. Furthermore, the remote unit 102 mayinclude a processor 202, a memory 204, an input device 206, a display208, a transmitter 210, and a receiver 212. In some embodiments, theinput device 206 and the display 208 are combined into a single device,such as a touchscreen. In certain embodiments, the remote unit 102 maynot include any input device 206 and/or display 208. In variousembodiments, the remote unit 102 may include one or more of theprocessor 202, the memory 204, the transmitter 210, and the receiver212, and may not include the input device 206 and/or the display 208.

The processor 202, in one embodiment, may include any known controllercapable of executing computer-readable instructions and/or capable ofperforming logical operations. For example, the processor 202 may be amicrocontroller, a microprocessor, a central processing unit (“CPU”), agraphics processing unit (“GPU”), an auxiliary processing unit, a fieldprogrammable gate array (“FPGA”), or similar programmable controller. Insome embodiments, the processor 202 executes instructions stored in thememory 204 to perform the methods and routines described herein. Theprocessor 202 is communicatively coupled to the memory 204, the inputdevice 206, the display 208, the transmitter 210, and the receiver 212.

The memory 204, in one embodiment, is a computer readable storagemedium. In some embodiments, the memory 204 includes volatile computerstorage media. For example, the memory 204 may include a RAM, includingdynamic RAM (“DRAM”), synchronous dynamic RAM (“SDRAM”), and/or staticRAM (“SRAM”). In some embodiments, the memory 204 includes non-volatilecomputer storage media. For example, the memory 204 may include a harddisk drive, a flash memory, or any other suitable non-volatile computerstorage device. In some embodiments, the memory 204 includes bothvolatile and non-volatile computer storage media. In some embodiments,the memory 204 stores data relating to synchronization signal blocks. Insome embodiments, the memory 204 also stores program code and relateddata, such as an operating system or other controller algorithmsoperating on the remote unit 102.

The input device 206, in one embodiment, may include any known computerinput device including a touch panel, a button, a keyboard, a stylus, amicrophone, or the like. In some embodiments, the input device 206 maybe integrated with the display 208, for example, as a touchscreen orsimilar touch-sensitive display. In some embodiments, the input device206 includes a touchscreen such that text may be input using a virtualkeyboard displayed on the touchscreen and/or by handwriting on thetouchscreen. In some embodiments, the input device 206 includes two ormore different devices, such as a keyboard and a touch panel.

The display 208, in one embodiment, may include any known electronicallycontrollable display or display device. The display 208 may be designedto output visual, audible, and/or haptic signals. In some embodiments,the display 208 includes an electronic display capable of outputtingvisual data to a user. For example, the display 208 may include, but isnot limited to, an LCD display, an LED display, an OLED display, aprojector, or similar display device capable of outputting images, text,or the like to a user. As another, non-limiting, example, the display208 may include a wearable display such as a smart watch, smart glasses,a heads-up display, or the like. Further, the display 208 may be acomponent of a smart phone, a personal digital assistant, a television,a table computer, a notebook (laptop) computer, a personal computer, avehicle dashboard, or the like.

In certain embodiments, the display 208 includes one or more speakersfor producing sound. For example, the display 208 may produce an audiblealert or notification (e.g., a beep or chime). In some embodiments, thedisplay 208 includes one or more haptic devices for producingvibrations, motion, or other haptic feedback. In some embodiments, allor portions of the display 208 may be integrated with the input device206. For example, the input device 206 and display 208 may form atouchscreen or similar touch-sensitive display. In other embodiments,the display 208 may be located near the input device 206.

The transmitter 210 is used to provide UL communication signals to thebase unit 104 and the receiver 212 is used to receive DL communicationsignals from the base unit 104. In some embodiments, the receiver 212may receive multiple synchronization signal blocks having differentpower levels. Although only one transmitter 210 and one receiver 212 areillustrated, the remote unit 102 may have any suitable number oftransmitters 210 and receivers 212. The transmitter 210 and the receiver212 may be any suitable type of transmitters and receivers. In oneembodiment, the transmitter 210 and the receiver 212 may be part of atransceiver.

FIG. 3 depicts one embodiment of an apparatus 300 that may be used forsynchronization signal block transmission. The apparatus 300 includesone embodiment of the base unit 104. Furthermore, the base unit 104 mayinclude a processor 302, a memory 304, an input device 306, a display308, a transmitter 310, and a receiver 312. As may be appreciated, theprocessor 302, the memory 304, the input device 306, the display 308,the transmitter 310, and the receiver 312 may be substantially similarto the processor 202, the memory 204, the input device 206, the display208, the transmitter 210, and the receiver 212 of the remote unit 102,respectively.

In some embodiments, the processor 302 may be used to determine powerlevels corresponding to each synchronization signal block of multiplesynchronization signal blocks transmitted using multiple transmit beams.In some embodiments, the transmitter 310 may be used to transmit themultiple synchronization signal blocks based on the power levels usingthe multiple transmit beams. Although only one transmitter 310 and onereceiver 312 are illustrated, the base unit 104 may have any suitablenumber of transmitters 310 and receivers 312. The transmitter 310 andthe receiver 312 may be any suitable type of transmitters and receivers.In one embodiment, the transmitter 310 and the receiver 312 may be partof a transceiver.

In certain embodiments, in response to the powers of synchronizationsignal blocks (“SS-blocks”) transmitted through different TX beams beingvariable, the base unit 104 may control the size and shape of thecoverage area by changing the SS-block transmission power. In suchembodiments, by controlling the SS-block transmission power, as well asthe TX beamforming vectors (direction and shape of the TX beams), thebase unit 104 may optimize the overall network coverage and networkcapacity to a desired cell coverage area resulting in less interferenceand fewer coverage holes. Accordingly, functions such as fractionalfrequency reuse or coverage enhancement may be implemented moreprecisely and more optimally by the base unit 104.

In various embodiments, for remote units 102 in a connected state (e.g.,RRC_CONNECTED), because the remote units 102 may conduct more detailedmeasurements based on CSI-RS (in addition to SS-block measurement) andreport the measurement results to a base unit 104, the base unit 104 mayhave more detailed information regarding their channel status and maybetter direct a remote unit 102 to handover to a cell, or a particularbeam. In certain embodiments, variable power of the SS-block throughdifferent DL TX beams may be more useful to optimize a remote unit 102in an idle state than a remote unit 102 in a connected state.

In some embodiments, a base unit 104 may control the individual powerlevels of SS-blocks transmitted through different TX beams. In variousembodiments, besides being used for mobility measurement, SS-blocks mayalso be used for beam management by remote units 102 in a connectedstate. For example, because SS-blocks may be transmitted incell-specific manner, they may be used for various steps of a DL beammanagement process.

In certain embodiments, for remote units 102 in a connected state, theremote units 102 may have selected (or have been handed over) to a bestcell, so cell selection may not be an issue. In one embodiment, beammanagement may use a remote unit 102 to measure reference signalreceived power (“RSRP”) of SS-blocks based on new radio (“NR”) secondarysynchronization signal (“SSS”) (and possibly as well as demodulationreference signal (“DMRS”) of PBCH) and report selected beams to the baseunit 104. In some embodiments, the remote unit 102 may choose a subsetof beams based on a measured SS-block RSRP and report the information tothe base unit 104. In various embodiments, in response to the SS-blocksbeing transmitted through different DL TX beams having different TXpower, a remote unit 102 in a connected state may need to know the powervalue (or power offset) of different SS-blocks in order to compare theirRSRPs. Accordingly, in some embodiments, the base unit 104 may includepower value (or equivalently power offset values) of the SS-blocks inRRC signaling when configuring an SS-block for a remote unit 102 in aconnected state.

In certain embodiments, nominal power of SS-blocks may be signaled inSIB. Further, in various embodiments, power offsets of individualSS-blocks may be signaled either in SIB message or RRC signaling. Insome embodiments, in response to the SS-block transmission power beingknown, a remote unit 102 may calculate and compare normalized RSRP forthe SS-blocks. In one embodiment, normalized RSRP may be defined as ameasured RSRP normalized with respect to power offset of the SS-blocks(as if the power offset is 0 dB for all the SS-blocks).

In certain embodiments, normalized SS-block RSRP power may be definedwith respect to SS-block transmission power offsets. In suchembodiments, a remote unit 102 may use normalized SS-block RSRP tocompare, select, and provide feedback corresponding to SS-blocks to abase unit 104 for beam management.

In various embodiments, besides SS-blocks, CSI-RS may also be used forDL beam management. In such embodiments, in response to both SS-blocksand CSI-RS being configured for remote unit 102 beam management, theRSRP of an SS-block may be compared with the RSRP of a CSI-RS port inorder to select and provide feedback for a number of good beams out ofall configured (SS-block and CSI-RS) beams. In certain embodiments, theremote unit 102 may know the transmission power of CSI-RS as well as thetransmission power of SS-blocks.

In some embodiments, a same transmission power may be used to transmitall the CSI-RS ports within a CSI-RS resource, while different CSI-RSresources may be transmitted with different TX power levels. In variousembodiments, the TX power or power offset of a CSI-RS resource may besignaled by a base unit 104 to a remote unit 102 in a connected statethrough RRC signaling in response to CSI-RS resources being configured.In certain embodiments, CSI-RS power (nominal power and offset forindividual CSI-RS resources) may be configured by RRC signaling. In oneembodiment, similar to SS-blocks, normalized RSRP may be defined forCSI-RS for a remote unit 102 to compare the beams between CSI-RS indifferent CSI-RS resources or between CSI-RS and SS-blocks.

In various embodiments, normalized CSI-RS RSRP power may be defined withrespect to SS-block transmission power offsets. In such embodiments, aremote unit 102 may use normalized SS-block RSRP to compare, select,and/or provide feedback CSI-RS RSRP to a base unit 104 for beammanagement.

FIG. 4 is a schematic flow chart diagram illustrating one embodiment ofa method 400 for synchronization signal block reception. In someembodiments, the method 400 is performed by an apparatus, such as theremote unit 102. In certain embodiments, the method 400 may be performedby a processor executing program code, for example, a microcontroller, amicroprocessor, a CPU, a GPU, an auxiliary processing unit, a FPGA, orthe like.

The method 400 may include receiving 402 multiple synchronization signalblocks having different power levels.

In one embodiment, the method 400 includes receiving power informationcorresponding to the power levels of the multiple synchronization signalblocks in radio resource control signaling. In a further embodiment, themethod 400 includes determining a normalized reference signal receivedpower corresponding to each synchronization signal block of the multiplesynchronization signal blocks using the power information. In certainembodiments, method 400 includes comparing the normalized referencesignal received power corresponding to each synchronization signal blockof the multiple synchronization signal blocks. In various embodiments,the method 400 includes transmitting feedback corresponding to thecomparison of the normalized reference signal received powercorresponding to each synchronization signal block of the multiplesynchronization signal blocks. In some embodiments, the method 400includes receiving nominal power information corresponding to the powerlevels of the multiple synchronization signal blocks in systeminformation blocks.

In certain embodiments, the method 400 includes receiving power offsetinformation corresponding to the power levels of the multiplesynchronization signal blocks in system information blocks, radioresource control signaling, or some combination thereof. In someembodiments, the method 400 includes receiving power informationcorresponding to channel state information reference signals in radioresource control signaling. In various embodiments, the powerinformation includes nominal power information, power offsetinformation, or some combination thereof.

In one embodiment, the method 400 includes determining a normalizedreference signal received power corresponding to channel stateinformation reference signals using the power information. In certainembodiments, the method 400 includes receiving channel state informationreference signal ports within a channel state information referencesignal resource at a same transmission power level. In some embodiments,the method 400 includes receiving different channel state informationreference signal resources at different transmission power levels. Invarious embodiments, the method 400 includes receiving power informationcorresponding to channel state information reference signal resources inradio resource control signaling. In one embodiment, the powerinformation includes nominal power information, power offsetinformation, or some combination thereof.

FIG. 5 is a schematic flow chart diagram illustrating one embodiment ofa method 500 for synchronization signal block transmission. In someembodiments, the method 500 is performed by an apparatus, such as thebase unit 104. In certain embodiments, the method 500 may be performedby a processor executing program code, for example, a microcontroller, amicroprocessor, a CPU, a GPU, an auxiliary processing unit, a FPGA, orthe like.

The method 500 may include determining 502 power levels corresponding toeach synchronization signal block of multiple synchronization signalblocks transmitted using multiple transmit beams. In some embodiments,the method 500 includes transmitting 504 the multiple synchronizationsignal blocks based on the power levels using the multiple transmitbeams.

In certain embodiments, the method 500 may include transmitting powerinformation corresponding to the power levels of the multiplesynchronization signal blocks in radio resource control signaling. Invarious embodiments, the method 500 may include transmitting nominalpower information corresponding to the power levels of the multiplesynchronization signal blocks in system information blocks. In someembodiments, the method 500 may include transmitting power offsetinformation corresponding to the power levels of the multiplesynchronization signal blocks in system information blocks, radioresource control signaling, or some combination thereof.

In certain embodiments, the method 500 may include transmitting powerinformation corresponding to channel state information reference signalsin radio resource control signaling. In some embodiments, the powerinformation includes nominal power information, power offsetinformation, or some combination thereof. In various embodiments, themethod 500 may include transmitting channel state information referencesignal ports within a channel state information reference signalresource at a same transmission power level. In one embodiment, themethod 500 may include transmitting different channel state informationreference signal resources at different transmission power levels. Incertain embodiments, the method 500 may include transmitting powerinformation corresponding to channel state information reference signalresources in radio resource control signaling. In various embodiments,the power information includes nominal power information, power offsetinformation, or some combination thereof.

Embodiments may be practiced in other specific forms. The describedembodiments are to be considered in all respects only as illustrativeand not restrictive. The scope of the invention is, therefore, indicatedby the appended claims rather than by the foregoing description. Allchanges which come within the meaning and range of equivalency of theclaims are to be embraced within their scope.

The invention claimed is:
 1. An apparatus comprising: a receiver that isconfigured to: receive a plurality of synchronization signal blockshaving power levels, wherein each synchronization signal block of theplurality of synchronization signal blocks is configured to be receivedon a different transmit beam at the power levels; and receive powerinformation corresponding to the power levels of the plurality ofsynchronization signal blocks; and a processor that determines anormalized reference signal received power corresponding to eachsynchronization signal block of the plurality of synchronization signalblocks using the power information.
 2. The apparatus of claim 1, whereinthe receiver receives the power information corresponding to the powerlevels of the plurality of synchronization signal blocks in radioresource control signaling.
 3. The apparatus of claim 1, wherein theprocessor compares the normalized reference signal received powercorresponding to each synchronization signal block of the plurality ofsynchronization signal blocks.
 4. The apparatus of claim 3, furthercomprising a transmitter that transmits feedback corresponding to thecomparison of the normalized reference signal received powercorresponding to each synchronization signal block of the plurality ofsynchronization signal blocks.
 5. The apparatus of claim 1, wherein thereceiver receives nominal power information corresponding to the powerlevels of the plurality of synchronization signal blocks in systeminformation blocks.
 6. The apparatus of claim 5, wherein the receiverreceives power offset information corresponding to the power levels ofthe plurality of synchronization signal blocks in system informationblocks, radio resource control signaling, or some combination thereof.7. The apparatus of claim 1, wherein the receiver receives powerinformation corresponding to channel state information reference signalsin radio resource control signaling.
 8. The apparatus of claim 7,wherein the power information comprises nominal power information, poweroffset information, or some combination thereof.
 9. The apparatus ofclaim 7, further comprising a processor that determines a normalizedreference signal received power corresponding to channel stateinformation reference signals using the power information.
 10. Theapparatus of claim 1, wherein the receiver receives channel stateinformation reference signal ports within a channel state informationreference signal resource at a same transmission power level.
 11. Theapparatus of claim 1, wherein the receiver receives different channelstate information reference signal resources at different transmissionpower levels.
 12. The apparatus of claim 1, wherein the receiverreceives power information corresponding to channel state informationreference signal resources in radio resource control signaling.
 13. Theapparatus of claim 12, wherein the power information comprises nominalpower information, power offset information, or some combinationthereof.
 14. A method at a user equipment, the method comprising:receiving a plurality of synchronization signal blocks having powerlevels, wherein each synchronization signal block of the plurality ofsynchronization signal blocks is configured to be received on adifferent transmit beam at the power levels; receiving power informationcorresponding to the power levels of the plurality of synchronizationsignal blocks; and determining a normalized reference signal receivedpower corresponding to each synchronization signal block of theplurality of synchronization signal blocks using the power information.15. The method of claim 14, further comprising receiving the powerinformation corresponding to the power levels of the plurality ofsynchronization signal blocks in radio resource control signaling. 16.The method of claim 14, further comprising comparing the normalizedreference signal received power corresponding to each synchronizationsignal block of the plurality of synchronization signal blocks.
 17. Themethod of claim 16, further comprising transmitting feedbackcorresponding to the comparison of the normalized reference signalreceived power corresponding to each synchronization signal block of theplurality of synchronization signal blocks.
 18. The method of claim 14,further comprising receiving nominal power information corresponding tothe power levels of the plurality of synchronization signal blocks insystem information blocks.
 19. The method of claim 18, furthercomprising receiving power offset information corresponding to the powerlevels of the plurality of synchronization signal blocks in systeminformation blocks, radio resource control signaling, or somecombination thereof.
 20. The method of claim 14, further comprisingreceiving power information corresponding to channel state informationreference signals in radio resource control signaling.